Building a pattern to define a topology and application environment using software components and software updates/fixes from external repositories from multiple vendors

ABSTRACT

A method, system and computer program product for building a pattern. An external framework engine identifies the software components, as well as code updates and/or code fixes, from the external repositories associated with different vendors. The framework engine then generates metadata using the identified software components and code updates and/or code fixes which may be used to determine the relationships between the software components. Furthermore, the framework engine generates configuration metadata to successfully link software components with a relationship. The framework engine then displays the software components available to be used to build the pattern, including the relationship linkages between the software components with a relationship along with the configuration metadata required to make a successful linkage. In this manner, the user will be able to build a pattern using software components provided from different vendors and be able to understand the relationship linkages between the software components.

TECHNICAL FIELD

The present invention relates generally to cloud computing, and moreparticularly to building a pattern to define a topology and applicationenvironment using software components and software updates/fixes fromexternal repositories from multiple vendors.

BACKGROUND

In a cloud computing environment, computing is delivered as a servicerather than a product, whereby shared resources, software andinformation are provided to computers and other devices as a meteredservice over a network, such as the Internet. In such an environment,computation, software, data access and storage services are provided tousers that do not require knowledge of the physical location andconfiguration of the system that delivers the services.

In a virtualized computer environment, such as may be implemented in aphysical cloud computing node of the cloud computing environment, thevirtualized computer environment includes a virtual operating system.The virtual operating system includes a common base portion and separateuser portions that all run on a physical computer. The physical computeris referred to as a host. The common base portion may be referred to asa hypervisor and each user portion may be called a guest. Each guest isa logical partition of the physical resources of the computer. A guestoperating system runs on each guest, and the guest appears to the guestoperating system as a real computer. Each guest operating system mayhost one or more virtual machines.

An administrator of the cloud computing environment may build a reusablepattern which defines the topology and application environment used toservice the customer (i.e., the user receiving the services provided bythe cloud computing environment) as well as satisfies the customerrequirements, such as application and processing requirements. Thepattern is an abstract model of the topology and application environmentthat encapsulates the installation, configuration and management ofmiddleware and applications, such as the middleware and applicationsthat run on the virtual machines in the physical cloud computing nodes.Such a pattern can be deployed repeatedly thereby avoiding the need toprovision these environments individually and manually.

Currently, such a pattern is built using only the software componentsthat are accessible from external repositories from the same vendor.Patterns cannot currently be built using software components fromseparate external repositories from different vendors. As a result, itbecomes more difficult to build a pattern that satisfies the customer'srequirements. Furthermore, since patterns can only be built usingsoftware components stored in external repositories from the samevendor, there is not currently a means for deriving relationshipsbetween various software components from different vendors.

BRIEF SUMMARY

In one embodiment of the present invention, a method for building apattern comprises identifying software components available from aplurality of external repositories associated with multiple vendors. Themethod further comprises identifying code updates and/or code fixes forsoftware components stored in the plurality of external repositories.The method additionally comprises generating metadata using theidentified software components and the identified code updates and/orcode fixes. Furthermore, the method comprises determining, by aprocessor, relationships between the identified software componentsusing the metadata. Additionally, the method comprises generatingconfiguration metadata to successfully link software components with arelationship. In addition, the method comprises displaying theidentified software components available to be used to build the patternas well as relationship linkages between the software components withthe relationship along with the configuration metadata.

Other forms of the embodiment of the method described above are in asystem and in a computer program product.

The foregoing has outlined rather generally the features and technicaladvantages of one or more embodiments of the present invention in orderthat the detailed description of the present invention that follows maybe better understood. Additional features and advantages of the presentinvention will be described hereinafter which may form the subject ofthe claims of the present invention.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

A better understanding of the present invention can be obtained when thefollowing detailed description is considered in conjunction with thefollowing drawings, in which:

FIG. 1 illustrates a network system configured in accordance with anembodiment of the present invention;

FIG. 2 illustrates a cloud computing environment in accordance with anembodiment of the present invention.

FIG. 3 illustrates a schematic of an exemplary cloud computing node in avirtualized computer environment in accordance with an embodiment of thepresent invention;

FIG. 4 illustrates a hardware configuration of an administrative serverconfigured in accordance with an embodiment of the present invention;and

FIGS. 5A-5B are a flowchart of a method for building a pattern usingsoftware components from external repositories from different vendors inaccordance with an embodiment of the present invention.

DETAILED DESCRIPTION

The present invention comprises a method, system and computer programproduct for building a pattern. In one embodiment, an external frameworkengine of the pattern engine (configured to build a pattern) identifiesthe software components available from the external repositoriesassociated with different vendors. Furthermore, the external frameworkengine identifies the code updates and/or code fixes (e.g., interimfixes, fix packs) for the software components stored in therepositories. The external framework engine then generates metadatausing the identified software components and identified code updatesand/or code fixes which may be used to determine the relationshipsbetween the software components. For example, the metadata may includeinformation, such as name, description, products that the updatesupports, update classification, download URL, applicability rules, andso on. The metadata may be used to determine any relationships betweenthe software components. Furthermore, the external framework enginegenerates configuration metadata to successfully link softwarecomponents with a relationship. The configuration metadata includes datathat is required to make a successful linkage (e.g., database name,port) between the software components. The external framework enginethen displays the software components available to be used to build thepattern, including the relationship linkages between the softwarecomponents with a relationship along with the configuration metadatarequired to make a successful linkage. In this manner, the user will beable to build a pattern using software components and code updatesand/or code fixes provided from different vendors. Furthermore, the userwill be able to understand the relationship linkages between thesoftware components and be able to provision these software componentsalong with the linkages dynamically.

In the following description, numerous specific details are set forth toprovide a thorough understanding of the present invention. However, itwill be apparent to those skilled in the art that the present inventionmay be practiced without such specific details. In other instances,well-known circuits have been shown in block diagram form in order notto obscure the present invention in unnecessary detail. For the mostpart, details considering timing considerations and the like have beenomitted inasmuch as such details are not necessary to obtain a completeunderstanding of the present invention and are within the skills ofpersons of ordinary skill in the relevant art.

It is understood in advance that although this disclosure includes adetailed description on cloud computing, implementation of the teachingsrecited herein are not limited to a cloud computing environment. Rather,the embodiments of the present invention are capable of beingimplemented in conjunction with any type of clustered computingenvironment now known or later developed.

In any event, the following definitions have been derived from the “TheNIST Definition of Cloud Computing” by Peter Mell and Timothy Grance,dated September 2011, which is cited on an Information DisclosureStatement filed herewith, and a copy of which is provided to the U.S.Patent and Trademark Office.

Cloud computing is a model for enabling ubiquitous, convenient,on-demand network access to a shared pool of configurable computingresources (e.g., networks, servers, storage, applications, and services)that can be rapidly provisioned and released with minimal managementeffort or service provider interaction. This cloud model is composed offive essential characteristics, three service models, and fourdeployment models.

Characteristics are as follows:

On-Demand Self-Service: A consumer can unilaterally provision computingcapabilities, such as server time and network storage, as needed,automatically without requiring human interaction with each service'sprovider.

Broad Network Access: Capabilities are available over a network andaccessed through standard mechanisms that promote use by heterogeneousthin or thick client platforms (e.g., mobile phones, tablets, laptopsand workstations).

Resource Pooling: The provider's computing resources are pooled to servemultiple consumers using a multi-tenant model, with different physicaland virtual resources dynamically assigned and reassigned according toconsumer demand. There is a sense of location independence in that theconsumer generally has no control or knowledge over the exact locationof the provided resources but may be able to specify location at ahigher level of abstraction (e.g., country, state or data center).Examples of resources include storage, processing, memory and networkbandwidth.

Rapid Elasticity: Capabilities can be elastically provisioned andreleased, in some cases automatically, to scale rapidly outward andinward commensurate with demand. To the consumer, the capabilitiesavailable for provisioning often appear to be unlimited and can bepurchased in any quantity at any time.

Measured Service: Cloud systems automatically control and optimizeresource use by leveraging a metering capability at some level ofabstraction appropriate to the type of service (e.g., storage,processing, bandwidth and active user accounts). Resource usage can bemonitored, controlled and reported providing transparency for both theprovider and consumer of the utilized service.

Service Models are as follows:

Software as a Service (SaaS): The capability provided to the consumer isto use the provider's applications running on a cloud infrastructure.The applications are accessible from various client devices througheither a thin client interface, such as a web browser (e.g., web-basede-mail) or a program interface. The consumer does not manage or controlthe underlying cloud infrastructure including network, servers,operating systems, storage, or even individual application capabilities,with the possible exception of limited user-specific applicationconfiguration settings.

Platform as a Service (PaaS): The capability provided to the consumer isto deploy onto the cloud infrastructure consumer-created or acquiredapplications created using programming languages, libraries, servicesand tools supported by the provider. The consumer does not manage orcontrol the underlying cloud infrastructure including networks, servers,operating systems or storage, but has control over the deployedapplications and possibly configuration settings for theapplication-hosting environment.

Infrastructure as a Service (IaaS): The capability provided to theconsumer is to provision processing, storage, networks and otherfundamental computing resources where the consumer is able to deploy andrun arbitrary software, which can include operating systems andapplications. The consumer does not manage or control the underlyingcloud infrastructure but has control over operating systems, storage anddeployed applications; and possibly limited control of select networkingcomponents (e.g., host firewalls).

Deployment Models are as follows:

Private Cloud: The cloud infrastructure is provisioned for exclusive useby a single organization comprising multiple consumers (e.g., businessunits). It may be owned, managed and operated by the organization, athird party or some combination of them, and it may exist on or offpremises.

Community Cloud: The cloud infrastructure is provisioned for exclusiveuse by a specific community of consumers from organizations that haveshared concerns (e.g., mission, security requirements, policy andcompliance considerations). It may be owned, managed and operated by oneor more of the organizations in the community, a third party, or somecombination of them, and it may exist on or off premises.

Public Cloud: The cloud infrastructure is provisioned for open use bythe general public. It may be owned, managed and operated by a business,academic or government organization, or some combination of them. Itexists on the premises of the cloud provider.

Hybrid Cloud: The cloud infrastructure is a composition of two or moredistinct cloud infrastructures (private, community or public) thatremain unique entities, but are bound together by standardized orproprietary technology that enables data and application portability(e.g., cloud bursting for load balancing between clouds).

Referring now to the Figures in detail, FIG. 1 illustrates a networksystem 100 configured in accordance with an embodiment of the presentinvention. Network system 100 includes a client device 101 connected toa cloud computing environment 102 via a network 103. Client device 101may be any type of computing device (e.g., portable computing unit,personal digital assistant (PDA), smartphone, laptop computer, mobilephone, navigation device, game console, desktop computer system,workstation, Internet appliance and the like) configured with thecapability of connecting to cloud computing environment 102 via network103.

Network 103 may be, for example, a local area network, a wide areanetwork, a wireless wide area network, a circuit-switched telephonenetwork, a Global System for Mobile Communications (GSM) network,Wireless Application Protocol (WAP) network, a WiFi network, an IEEE802.11 standards network, various combinations thereof, etc. Othernetworks, whose descriptions are omitted here for brevity, may also beused in conjunction with system 100 of FIG. 1 without departing from thescope of the present invention.

Cloud computing environment 102 is used to deliver computing as aservice to client device 101 implementing the model discussed above. Anembodiment of cloud computing environment 102 is discussed below inconnection with FIG. 2.

FIG. 2 illustrates cloud computing environment 102 in accordance with anembodiment of the present invention. As shown, cloud computingenvironment 102 includes one or more cloud computing nodes 201 withwhich local computing devices used by cloud consumers, such as, forexample, personal digital assistant (PDA) or cellular telephone 202,desktop computer 203, laptop computer 204, and/or automobile computersystem 205 may communicate. Nodes 201 may communicate with one another.They may be grouped (not shown) physically or virtually, in one or morenetworks, such as Private, Community, Public, or Hybrid clouds asdescribed hereinabove, or a combination thereof. This allows cloudcomputing environment 102 to offer infrastructure, platforms and/orsoftware as services for which a cloud consumer does not need tomaintain resources on a local computing device. A description of aschematic of an exemplary cloud computing node 201 is provided below inconnection with FIG. 3. It is understood that the types of computingdevices 202, 203, 204, 205 shown in FIG. 2, which may represent clientdevice 101 of FIG. 1, are intended to be illustrative and that cloudcomputing nodes 201 and cloud computing environment 102 can communicatewith any type of computerized device over any type of network and/ornetwork addressable connection (e.g., using a web browser). Program codelocated on one of nodes 201 may be stored on a computer recordablestorage medium in one of nodes 201 and downloaded to computing devices202, 203, 204, 205 over a network for use in these computing devices.For example, a server computer in computing nodes 201 may store programcode on a computer readable storage medium on the server computer. Theserver computer may download the program code to computing device 202,203, 204, 205 for use on the computing device.

Referring now to FIG. 3, FIG. 3 illustrates cloud computing nodes201A-201N, where N is a positive integer number, in a virtualizedcomputer environment in accordance with an embodiment of the presentinvention. Cloud computing nodes 201A-201N may collectively orindividually be referred to as cloud computing nodes 201 or cloudcomputing node 201, respectively. Cloud computing nodes 201A-201N areeach coupled to an administrative server 301 configured to provide datacenter-level functions of communicating with hypervisors on cloudcomputing nodes 201 to install virtual machines, terminate/suspendvirtual machines and relocate virtual machines from one cloud computingnode 201 to another within the data center. A description of thehardware configuration of administrative server 301 is provided furtherbelow in connection with FIG. 4.

With reference now to cloud computing node 201A, cloud computing node201A includes a virtual operating system 302A. Operating system 302Aexecutes on a real or physical computer 303A. Real computer 303Aincludes one or more processors 304A, a memory 305A (also referred toherein as the host physical memory), one or more disk drives 306A andthe like. Other components of real computer 303A are not discussedherein for the sake of brevity.

Virtual operating system 302A further includes user portions 307A-307B(identified as “Guest 1” and Guest 2,” respectively, in FIG. 3),referred to herein as “guests.” Each guest 307A, 307B is capable offunctioning as a separate system. That is, each guest 307A-307B can beindependently reset, host a guest operating system 308A-308B,respectively, (identified as “Guest 1 O/S” and “Guest 2 O/S,”respectively, in FIG. 3) and operate with different programs. Anoperating system or application program running in guest 307A, 307Bappears to have access to a full and complete system, but in reality,only a portion of it is available.

Each guest operating system 308A, 308B may host one or more virtualmachine applications 309A-309C (identified as “VM 1,” “VM 2,” and “VM3,” respectively, in FIG. 3), such as Java™ virtual machines. Forexample, guest operating system 308A hosts virtual machine applications309A-309B. Guest operating system 308B hosts virtual machine application309C.

Virtual operating system 302A further includes a common base portion310A, referred to herein as a hypervisor. Hypervisor 310A may beimplemented in microcode running on processor 304A or it may beimplemented in software as part of virtual operating system 302A.Hypervisor 310A is configured to manage and enable guests 307A, 307B torun on a single host.

As discussed above, virtual operating system 302A and its componentsexecute on physical or real computer 303A. These software components maybe loaded into memory 305A for execution by processor 304A.

As also discussed above, cloud computing environment 102 (FIG. 2) caninclude multiple cloud computing nodes 201A-201N as is shown in FIG. 3.In one embodiment, each cloud computing node 201A-201N is configuredsimilarly as previously discussed cloud computing node 201A. Forexample, cloud computing node 201N is configured similarly as cloudcomputing node 201A. Cloud computing node 201N includes the sameelements as cloud computing node 201A. For example, guests 307C-307D(identified as “Guest 3” and “Guest 4,” respectively, in FIG. 3) arefunctionally the same as guests 307A-307B. Similarly, guest operatingsystems 308C-308D (identified as “Guest 3 O/S” and “Guest 4 O/S,”respectively, in FIG. 3) are functionally the same as guest operatingsystems 308A-308B. Virtual machines 309D-309E (identified as “VM 4” and“VM 5,” respectively, in FIG. 3) are functionally the same as virtualmachines 309A-309C. Furthermore, hypervisor 310B is functionally thesame as hypervisor 310A. Hence, the discussion of cloud computing node201A applies to each cloud computing node 201, including cloud computingnode 201N. In one embodiment, each cloud computing node 201 can beconfigured differently and the physical hardware, hypervisors and othercomponents may be different as well.

Guests 307A-307D may collectively or individually be referred to asguests 307 or guest 307, respectively. Guest operating systems 308A-308Dmay collectively or individually be referred to as guest operatingsystems 308 or guest operating system 308, respectively. Virtualmachines 309A-309E may collectively or individually be referred to asvirtual machines 309 or virtual machine 309, respectively. Hypervisors310A-310B may collectively or individually be referred to as hypervisors310 or hypervisor 310, respectively.

FIG. 3 is not to be limited in scope to a particular number of cloudcomputing nodes 201 and each cloud computing node 201 may include anynumber of guests 307, guest operating systems 308, virtual machines 309,etc. Furthermore, cloud computing nodes 201 include other componentsthat were not discussed herein for the sake of brevity. Hence, cloudcomputing node 201 is not to be limited in scope to the elementsdepicted in FIG. 3.

Referring again to FIG. 3, in some embodiments, administrative server301 supports a module, referred to herein as the pattern engine 311,configured to build a pattern to be provisioned at the virtual machinedeployment time. A “pattern,” as used herein, refers to an abstractmodel of the topology and application environment that encapsulates theinstallation, configuration and management of middleware andapplications, such as the middleware and applications that run onvirtual machines 309. Such a pattern can be deployed repeatedly therebyavoiding the need to provision these environments individually andmanually.

In one embodiment, pattern engine 311 includes a module, referred toherein as the external framework engine 312, configured to enable thebuilding of the pattern using software components from externalrepositories from different vendors as discussed further below.

As illustrated in FIG. 3, external framework engine 312 is connected tovarious repositories, such as repositories 313A-313C (identified as“Repository 1,” “Repository 2,” and “Repository 3,” respectively, inFIG. 3) via plugins 314A-314C, respectively (identified as “ExternalRepository 1 Plugin,” “External Repository 2 Plugin,” and “ExternalRepository 3 Plugin,” respectively, in FIG. 3). Repositories 313A-313Cmay collectively or individually be referred to as repositories 313 orrepository 313, respectively. Furthermore, plugins 314A-314C maycollectively or individually be referred to as plugins 314 or plugin314, respectively.

In one embodiment, repositories 313 store software components (e.g.,application server, database server) as well as any software updatesand/or fixes for any of the software components stored in repository313. These repositories 313 may be associated with different vendors.That is, each repository 313 may store software components (e.g.,application server, database server) as well as any software updatesand/or fixes for any of the software components stored in repository 313for a specific vendor. As a result, a group of repositories 313 maystore software components as well as any software updates and/or fixesfor various vendors. While FIG. 3 illustrates three repositories 313,the present invention is not to be limited in scope to any particularnumber of repositories 313. Furthermore, multiple repositories 313(e.g., repositories 313A-313B) may store software components as well asany software updates and/or fixes from the same vendor; however, theentire group of repositories 313 (e.g., repositories 313A-313C) willstore software components as well as any software updates and/or fixesfrom different vendors.

As discussed above, external framework engine 312 is connected tovarious repositories 313 via plugins 314. A plugin 314, as used herein,refers to a software component that enables external framework engine312 to query or access repository 313 for a particular vendor. Forexample, plugin 314A enables external framework engine 312 to accessrepository 313A. In another example, plugin 314B enables externalframework engine 312 to access repository 313B and plugin 314C enablesexternal framework engine 312 to access repository 313C. As a result,each plugin 314 may be specifically tailored to allow external frameworkengine 312 to identify software components, including any new softwarecomponents, as well as any software updates and/or fixes in repository313 for that vendor as discussed further below in connection with FIGS.5A-5B. In one embodiment, the identified software components as well asany software updates and/or fixes may be stored in a cache 315 (labeledas “Raw Data Cache” in FIG. 3).

External framework engine 312 uses the identified software components aswell as any software updates and/or fixes to generate metadata to beused to determine the relationships between the software components. Forexample, the metadata may include information, such as name,description, products that the update supports, update classification,download URL, applicability rules, and so on. The metadata may be usedto determine any relationships between the software components. In oneembodiment, the metadata may be stored in a cache 316 (labeled as“Metadata Cache” in FIG. 3).

External framework engine 312 may further be configured to generateconfiguration metadata to successfully link the software components witha relationship. In one embodiment, the configuration metadata may bestored in cache 316. In this manner, software components (e.g.,application server, database server) with a relationship linkage can bepresented to the user (e.g., presented via a user interface of clientdevice 101 of FIG. 1) along with configuration metadata required to makea successful linkage (e.g., database name, port). At provisioning time,the software components along with the linkages are dynamicallyprovisioned as discussed further below in connection with FIGS. 5A-5B.

Referring now to FIG. 4, FIG. 4 illustrates a hardware configuration ofadministrative server 301 (FIG. 3) which is representative of a hardwareenvironment for practicing the present invention. Administrative server301 has a processor 401 coupled to various other components by systembus 402. An operating system 403 runs on processor 401 and providescontrol and coordinates the functions of the various components of FIG.4. An application 404 in accordance with the principles of the presentinvention runs in conjunction with operating system 403 and providescalls to operating system 403 where the calls implement the variousfunctions or services to be performed by application 404. Application404 may include, for example, a program (e.g., external framework engine312 of FIG. 3) for building a pattern using software components fromexternal repositories 313 (FIG. 3) from different vendors as discussedfurther below in association with FIGS. 5A-5B.

Referring again to FIG. 4, read-only memory (“ROM”) 405 is coupled tosystem bus 402 and includes a basic input/output system (“BIOS”) thatcontrols certain basic functions of administrative server 301. Randomaccess memory (“RAM”) 406 and disk adapter 407 are also coupled tosystem bus 402. It should be noted that software components includingoperating system 403 and application 404 may be loaded into RAM 406,which may be administrative server's 301 main memory for execution. Diskadapter 407 may be an integrated drive electronics (“IDE”) adapter thatcommunicates with a disk unit 408, e.g., disk drive. It is noted thatthe program for building a pattern using software components fromexternal repositories 313 from different vendors, as discussed furtherbelow in association with FIGS. 5A-5B, may reside in disk unit 408 or inapplication 404.

Administrative server 301 may further include a communications adapter409 coupled to bus 402. Communications adapter 409 interconnects bus 402with an outside network (e.g., network 103 of FIG. 1).

The present invention may be a system, a method, and/or a computerprogram product. The computer program product may include a computerreadable storage medium (or media) having computer readable programinstructions thereon for causing a processor to carry out aspects of thepresent invention.

The computer readable storage medium can be a tangible device that canretain and store instructions for use by an instruction executiondevice. The computer readable storage medium may be, for example, but isnot limited to, an electronic storage device, a magnetic storage device,an optical storage device, an electromagnetic storage device, asemiconductor storage device, or any suitable combination of theforegoing. A non-exhaustive list of more specific examples of thecomputer readable storage medium includes the following: a portablecomputer diskette, a hard disk, a random access memory (RAM), aread-only memory (ROM), an erasable programmable read-only memory (EPROMor Flash memory), a static random access memory (SRAM), a portablecompact disc read-only memory (CD-ROM), a digital versatile disk (DVD),a memory stick, a floppy disk, a mechanically encoded device such aspunch-cards or raised structures in a groove having instructionsrecorded thereon, and any suitable combination of the foregoing. Acomputer readable storage medium, as used herein, is not to be construedas being transitory signals per se, such as radio waves or other freelypropagating electromagnetic waves, electromagnetic waves propagatingthrough a waveguide or other transmission media (e.g., light pulsespassing through a fiber-optic cable), or electrical signals transmittedthrough a wire.

Computer readable program instructions described herein can bedownloaded to respective computing/processing devices from a computerreadable storage medium or to an external computer or external storagedevice via a network, for example, the Internet, a local area network, awide area network and/or a wireless network. The network may comprisecopper transmission cables, optical transmission fibers, wirelesstransmission, routers, firewalls, switches, gateway computers and/oredge servers. A network adapter card or network interface in eachcomputing/processing device receives computer readable programinstructions from the network and forwards the computer readable programinstructions for storage in a computer readable storage medium withinthe respective computing/processing device.

Computer readable program instructions for carrying out operations ofthe present invention may be assembler instructions,instruction-set-architecture (ISA) instructions, machine instructions,machine dependent instructions, microcode, firmware instructions,state-setting data, or either source code or object code written in anycombination of one or more programming languages, including an objectoriented programming language such as Smalltalk, C++ or the like, andconventional procedural programming languages, such as the “C”programming language or similar programming languages. The computerreadable program instructions may execute entirely on the user'scomputer, partly on the user's computer, as a stand-alone softwarepackage, partly on the user's computer and partly on a remote computeror entirely on the remote computer or server. In the latter scenario,the remote computer may be connected to the user's computer through anytype of network, including a local area network (LAN) or a wide areanetwork (WAN), or the connection may be made to an external computer(for example, through the Internet using an Internet Service Provider).In some embodiments, electronic circuitry including, for example,programmable logic circuitry, field-programmable gate arrays (FPGA), orprogrammable logic arrays (PLA) may execute the computer readableprogram instructions by utilizing state information of the computerreadable program instructions to personalize the electronic circuitry,in order to perform aspects of the present invention.

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems), and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer readable program instructions.

These computer readable program instructions may be provided to aprocessor of a general purpose computer, special purpose computer, orother programmable data processing apparatus to produce a machine, suchthat the instructions, which execute via the processor of the computeror other programmable data processing apparatus, create means forimplementing the functions/acts specified in the flowchart and/or blockdiagram block or blocks. These computer readable program instructionsmay also be stored in a computer readable storage medium that can directa computer, a programmable data processing apparatus, and/or otherdevices to function in a particular manner, such that the computerreadable storage medium having instructions stored therein comprises anarticle of manufacture including instructions which implement aspects ofthe function/act specified in the flowchart and/or block diagram blockor blocks.

The computer readable program instructions may also be loaded onto acomputer, other programmable data processing apparatus, or other deviceto cause a series of operational steps to be performed on the computer,other programmable apparatus or other device to produce a computerimplemented process, such that the instructions which execute on thecomputer, other programmable apparatus, or other device implement thefunctions/acts specified in the flowchart and/or block diagram block orblocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods, and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof instructions, which comprises one or more executable instructions forimplementing the specified logical function(s). In some alternativeimplementations, the functions noted in the block may occur out of theorder noted in the figures. For example, two blocks shown in successionmay, in fact, be executed substantially concurrently, or the blocks maysometimes be executed in the reverse order, depending upon thefunctionality involved. It will also be noted that each block of theblock diagrams and/or flowchart illustration, and combinations of blocksin the block diagrams and/or flowchart illustration, can be implementedby special purpose hardware-based systems that perform the specifiedfunctions or acts or carry out combinations of special purpose hardwareand computer instructions.

As stated in the Background section, an administrator of the cloudcomputing environment may build a reusable pattern which defines thetopology and application environment used to service the customer (i.e.,the user receiving the services provided by the cloud computingenvironment) as well as satisfies the customer requirements, such asapplication and processing requirements. The pattern is an abstractmodel of the topology and application environment that encapsulates theinstallation, configuration and management of middleware andapplications, such as the middleware and applications that run on thevirtual machines in the physical cloud computing nodes. Such a patterncan be deployed repeatedly thereby avoiding the need to provision theseenvironments individually and manually. Currently, such a pattern isbuilt using only the software components that are accessible fromexternal repositories from the same vendor. Patterns cannot currently bebuilt using software components from separate external repositories fromdifferent vendors. As a result, it becomes more difficult to build apattern that satisfies the customer's requirements. Furthermore, sincepatterns can only be built using software components stored in externalrepositories from the same vendor, there is not currently a means forderiving relationships between various software components fromdifferent vendors.

The principles of the present invention provide a means for building apattern using software components from external repositories fromdifferent vendors as well as displaying to the user, in connection withbuilding the pattern, relationship linkages between software componentsalong with configuration metadata required to make a successful linkagethereby enabling the software components along with the linkages to bedynamically provisioned as discussed further below in connection withFIGS. 5A-5B.

FIGS. 5A-5B are a flowchart of a method 500 for building a pattern usingsoftware components from external repositories 313 (FIG. 3) fromdifferent vendors in accordance with an embodiment of the presentinvention.

Referring to FIG. 5A, in conjunction with FIGS. 1-4, in step 501,external framework engine 312 identifies software components (e.g.,application server, database server) available from repositories 313associated with different vendors.

In step 502, external framework engine 312 identifies the code updatesand/or code fixes (e.g., interim fixes, fix packs) (the phrase “codeupdates/fixes” in FIGS. 5A and 5B refers to code updates and/or codefixes) for the software components stored in repositories 313.

In step 503, external framework engine 312 stores the identifiedsoftware components and code updates and/or code fixes, such as in cache315. In one embodiment, cache 315 is used to hold the raw data fromrepository 313, such as software components and code updates and/or codefixes, so as to avoid the lengthy time in querying repository 313 toobtain the requested data for future requests for the same data.

In step 504, external framework engine 312 generates metadata using theidentified software and identified code updates and/or code fixes. Themetadata may be used to determine the relationships between the softwarecomponents. For example, the metadata may include information, such asname, description, products that the update supports, updateclassification, download URL, applicability rules, and so on. Themetadata may be used to determine any relationships between the softwarecomponents.

In step 505, external framework engine 312 stores the generatedmetadata, such as in cache 316.

In step 506, external framework engine 312 determines the relationshipsbetween the software components using the generated metadata asdiscussed above.

In step 507, external framework engine 312 generates configurationmetadata to successfully link software components with a relationship.In one embodiment, the configuration metadata is stored in cache 316.The configuration metadata includes data that is required to make asuccessful linkage (e.g., database name, port) between the softwarecomponents.

In step 508, external framework engine 312 displays the softwarecomponents available to be used to build the pattern, including therelationship linkages between the software components with arelationship along with the configuration metadata required to make asuccessful linkage. In this manner, the user (e.g., user of clientdevice 101) will be able to build a pattern using software componentsand code updates and/or code fixes provided from different vendors.Furthermore, the user will be able to understand the relationshiplinkages between the software components and be able to provision thesesoftware components along with the linkages dynamically as discussedfurther below.

In step 509, external framework engine 312 receives a selection ofsoftware components out of the software components displayed in step 508to be included in the pattern from the user.

Referring now to FIG. 5B, in conjunction with FIGS. 1-4, in step 510,external framework engine 312 presents the available code updates and/orcode fixes, if any, for the selected software components (softwarecomponents selected in step 509 of FIG. 5A) to the user in response tothe user selecting the software components to be included in the patternin step 509.

In step 511, a determination is made by external framework engine 312 asto whether the user provided a request to include any of the presentedcode updates and/or code fixes in the pattern.

If the user did not provide a request to include any of the presentedcode updates and/or code fixes in the pattern, then, in step 512, thepattern will not include any code updates and/or code fixes.

If, however, the user provided a request to include one or more of thecode updates and/or code fixes presented to the user in step 510 in thepattern, then, in step 513, external framework engine 312 will includethose code updates and/or code fixes selected by the user in thepattern.

In step 514, external framework engine 312 builds the pattern with theselected software components and the selected code updates and/or codefixes, if any.

In step 515, external framework engine 312 provisions the pattern at thevirtual machine deployment time. As discussed above, the pattern is anabstract model of the topology and application environment thatencapsulates the installation, configuration and management ofmiddleware and applications, such as the middleware and applicationsthat run on virtual machines 309. As a result, the software componentsand any code updates and/or code fixes are provisioned at the virtualmachine deployment time.

The descriptions of the various embodiments of the present inventionhave been presented for purposes of illustration, but are not intendedto be exhaustive or limited to the embodiments disclosed. Manymodifications and variations will be apparent to those of ordinary skillin the art without departing from the scope and spirit of the describedembodiments. The terminology used herein was chosen to best explain theprinciples of the embodiments, the practical application or technicalimprovement over technologies found in the marketplace, or to enableothers of ordinary skill in the art to understand the embodimentsdisclosed herein.

The invention claimed is:
 1. A computer program product for building apattern, the computer program product comprising a computer readablestorage medium having program code embodied therewith, the program codecomprising the programming instructions for: identifying softwarecomponents available from a plurality of external repositoriesassociated with multiple vendors; identifying code updates and/or codefixes for software components stored in said plurality of externalrepositories; generating metadata using said identified softwarecomponents and said identified code updates and/or code fixes;determining relationships between said identified software componentsusing said metadata; generating configuration metadata to successfullylink software components with a relationship; displaying said identifiedsoftware components available to be used to build said pattern as wellas relationship linkages between said software components with saidrelationship along with said configuration metadata; receiving aselection of one or more software components from said displayedsoftware components to be included in said pattern; and building saidpattern with said selected one or more software components.
 2. Thecomputer program product as recited in claim 1, wherein the program codefurther comprises the programming instructions for: presenting availablecode updates and/or code fixes for one or more of said one or moreselected software components to a user in response to said userselecting said one or more software components to be included in saidpattern.
 3. The computer program product as recited in claim 2, whereinthe program code further comprises the programming instructions for:including one or more of said code updates and/or code fixes presentedto said user in said pattern in response to said user selecting said oneor more code updates and/or code fixes to be included in said pattern.4. The computer program product as recited in claim 3, wherein theprogram code further comprises the programming instructions for:building said pattern with said selected one or more software componentsand said selected one or more code updates and/or code fixes.
 5. Thecomputer program product as recited in claim 4, wherein the program codefurther comprises the programming instructions for: provisioning saidpattern at a virtual machine deployment time.
 6. A system, comprising: amemory unit for storing a computer program for building a pattern; and aprocessor coupled to the memory unit, wherein the processor isconfigured to execute the program instructions of the computer programcomprising: identifying software components available from a pluralityof external repositories associated with multiple vendors; identifyingcode updates and/or code fixes for software components stored in saidplurality of external repositories; generating metadata using saididentified software components and said identified code updates and/orcode fixes; determining relationships between said identified softwarecomponents using said metadata; generating configuration metadata tosuccessfully link software components with a relationship; displayingsaid identified software components available to be used to build saidpattern as well as relationship linkages between said softwarecomponents with said relationship along with said configurationmetadata; receiving a selection of one or more software components fromsaid displayed software components to be included in said pattern; andbuilding said pattern with said selected one or more softwarecomponents.
 7. The system as recited in claim 6, wherein the programinstructions of the computer program further comprises: presentingavailable code updates and/or code fixes for one or more of said one ormore selected software components to a user in response to said userselecting said one or more software components to be included in saidpattern.
 8. The system as recited in claim 7, wherein the programinstructions of the computer program further comprises: including one ormore of said code updates and/or code fixes presented to said user insaid pattern in response to said user selecting said one or more codeupdates and/or code fixes to be included in said pattern.
 9. The systemas recited in claim 8, wherein the program instructions of the computerprogram further comprises: building said pattern with said selected oneor more software components and said selected one or more code updatesand/or code fixes.
 10. The system as recited in claim 9, wherein theprogram instructions of the computer program further comprises:provisioning said pattern at a virtual machine deployment time.